|
|
|
|
|
|
|
and the customer is outside the scope of the Samsona Bank Teller System. Recall from the problem statement that your system helps the teller to better facilitate the process of maintaining bank accounts. The teller interfaces with her customer in one context and then interfaces with your system in another. Your problem domain is concerned only with the second context. Business process engineering (the designing and modeling of business tasks/responsibilities and events at the enterprise or workgroup level) would likely be concerned with the first context. |
|
|
|
|
|
|
|
|
Tip
If you encounter new, possibly helpful requirements that are outside the scope of your current project increment or iteration, the team's architect and project manager should decide in which increment/iteration of the software the requirements should be incorporated. An increment incorporates a new feature or subsystem to the application. An iteration results in an EXE file being released to users or another project team. |
|
|
|
|
|
|
|
|
|
Returning to your list of candidate actors/classes, you'll notice that teller is obviously an important noun because this is the main actor who will use your system. Therefore, you now have your first actor. The noun Samsona Bank Teller System is the name of your system, and at this point, let's assume that you don't have a compelling reason to model it as an actor or a class. Therefore, it's no longer a viable candidate. |
|
|
|
|
|
|
|
|
Note
In general, you wouldn't model your application as an actor or a class. However, it could be modeled as a subsystem or package if it were part of a suite of applications. |
|
|
|
|
|
|
|
|
|
The noun process describes the act of maintaining accounts and is too vague to be anything more than a descriptive noun that helps express the problem statement more fully for the system developers. It, too, is no longer a viable candidate. |
|
|
|
|
|
|
|
|
The noun bank accounts is a collection of accounts. Within the sentence that mentions bank accounts, you see that they are the main objects that the teller manages and, as a collection, are a strong candidate for a class (or more specifically, a collection class). |
|
|
|
|
|
|
|
|
Tip
If you discover plural nouns in your problem statement that are of significance to your system, make a design note to yourself that such nouns might be a collection class, which Visual Basic supports. An example of plural nouns is a noun with an s at the end that implies more than one of the noun. |
|
|
|
|
|
|